The system creates error and log messages that you can customize to meet your company's needs.
The message system is enabled by default. Without making any modifications, it is fully functional. Each executed system program (GenTrn, GenData, GenPrint, and so on) appends output messages to the appropriate log or error file.
When an error or log message occurs, the system writes the information to a token file named MSGFILE.DAT. A second step converts or translates the output into log and error files, which are typically named LOGFILE.DAT and ERRFILE.DAT.
By default, this translation step occurs before each program’s termination so the system is compatible with earlier versions. You can, however, delay this step and execute it manually using the TRANSLAT utility (see the Utilities Reference for more information). This lets you translate the message and error information after all system programs have completed their processing cycle for a given batch run.
| Note | Typically, you will want to use system defaults as you implement your system; this lets you spot errors after each processing step. Once your system is implemented and is running without error, you may want to delay the translation process to improve performance. See Controlling the Translation Process for more information. |
Delaying the translation process can sometimes improve throughput performance—especially in batch implementations that typically run without errors.
This translation process, delayed or not, gives you flexibility in the type of options you can use; increases the amount of information that can be generated; and lets you control message formatting and language.
© Copyright 2015, Oracle and/or its affiliates. All rights reserved. Legal notices.